Message oriented middleware with integrated rules engine

ABSTRACT

Embodiments of the present invention provide a method, system and computer program product for the integration of a rules engine with message oriented middleware. In an embodiment of the invention, a method for managing a messaging component in message oriented middleware has been provided. The method includes creating shared memory in the memory of a computer and adding or deleting tokens in the shared memory corresponding to objects such as messages and message queues, created in and removed from, respectively, in a messaging component of message oriented middleware. The method additionally includes applying rules in a rules engine to the tokens in the shared memory. Finally, the method includes directing management operations in the messaging component responsive to the applied rules by the rules engine.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a Continuation of U.S. application Ser. No.13/406,686, filed Feb. 28, 2012, which is a Divisional of U.S.application Ser. No. 13/173,052, filed Jun. 30, 2011, the entirety ofeach which is incorporated herein by reference.

BACKGROUND OF THE INVENTION

Field of the Invention

The present invention relates to message passing and more particularlyto message passing in message oriented middleware.

Description of the Related Art

Message oriented middleware refers to a programmatic infrastructure thatsupports the exchange of messages between distributed computing systems.In this regard, the message brokering operability of message orientedmiddleware allows application modules to be distributed overheterogeneous platforms while communicating through message queuesmanaged by a messaging component and reduces the complexity ofdeveloping applications that span multiple operating systems and networkprotocols. In this regard, the message oriented middleware creates adistributed communications layer that insulates the applicationdeveloper from the details of the various operating system and networkinterfaces.

Typically, in the simplest form, administration of message orientedmiddleware takes the form of embedded commands provided by the messageoriented middleware that allows a system administrator to create andmodify properties of the messaging component. With access to a set ofembedded commands, the system administrator then can decide whichproperties of the messaging component to modify and when. With this typeof setup, the administrator needs only a basic understanding of themessaging component of the message oriented middleware. Further, thistype of administration generally works on a small scale. However, it iswidely understood that message oriented middleware administrationthrough embedded commands scales poorly in a multi-message componentdeployment.

The deployment of a management infrastructure tool such as a rulesengine seeks to address the lack of scalability in the above-mentionedapproach. A rules engine interacts with message oriented middlewarethrough interprocess communications in order to retrieve operationalcharacteristics of the middleware including message puts and gets, andprovides operational directives through interprocess communications tothe middleware in response to the application of rules to the retrievedoperational characteristics. The use of a rules engine to manage theoperation of message oriented middleware, however, it not withoutlimitation.

In particular, as the rules engine is typically removed from the messageoriented middleware, data exchanged between the two using interprocesscommunications is slow, since a network round trip is required.Therefore, there is usually an incentive to minimize the amount of datapassed to the control station, thus, effectively limiting the amount ofinformation available to the control station. In the alternative, arules engine accessing an application programming interface (API) to themessage oriented middleware addresses some of the concerns in respect toslow data exchanges. However, to the extent that the rules engine andmessage oriented middleware are separate, with the rules engine beingmaintained by a completely separate group of developers from thedevelopers maintaining the messaging oriented middleware, there arepractical difficulties to making the rules engine work effectively withthe messaging component and delays in upgrading the rules engine toaccount for new features in the messaging oriented middleware oftenarise.

BRIEF SUMMARY OF THE INVENTION

Embodiments of the present invention address deficiencies of the art inrespect to the management of message oriented middleware and provide anovel and non-obvious method, system and computer program product forthe integration of a rules engine with message oriented middleware. Inan embodiment of the invention, a method for managing a messagingcomponent in message oriented middleware has been provided. The methodincludes creating shared memory in the memory of a computer and addingor deleting tokens in the shared memory corresponding to objects such asmessages and message queues, created in and removed from, respectively,in a messaging component of message oriented middleware, or topics orsubscriptions or log file space for messages queues in the messagingcomponent. The method additionally includes applying rules in a rulesengine to the tokens in the shared memory. Finally, the method includesdirecting management operations in the messaging component responsive tothe applied rules by the rules engine.

Additional aspects of the invention will be set forth in part in thedescription which follows, and in part will be obvious from thedescription, or may be learned by practice of the invention. The aspectsof the invention will be realized and attained by means of the elementsand combinations particularly pointed out in the appended claims. It isto be understood that both the foregoing general description and thefollowing detailed description are exemplary and explanatory only andare not restrictive of the invention, as claimed.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute partof this specification, illustrate embodiments of the invention andtogether with the description, serve to explain the principles of theinvention. The embodiments illustrated herein are presently preferred,it being understood, however, that the invention is not limited to theprecise arrangements and instrumentalities shown, wherein:

FIG. 1 is a pictorial illustration of a process for managing a messagingcomponent in message oriented middleware;

FIG. 2 is a schematic illustration of a message processing systemconfigured with an integrated rules engine for managing a messagingcomponent in message oriented middleware; and,

FIG. 3 is a flow chart illustrating a process for managing a messagingcomponent in message oriented middleware.

DETAILED DESCRIPTION OF THE INVENTION

Embodiments of the invention provide for a message processing systemconfigured with an integrated rules engine for managing a messagingcomponent in message oriented middleware. In accordance with anembodiment of the invention, a rules engine can be coupled to amessaging component within message oriented middleware. A working memoryof the rules engine can be established in shared memory of the messageoriented middleware and tokens can be created and removed in the workingmemory by the messaging component to correspond to the creation andremoval of objects such as message queues, messages in message queues,topics, subscriptions or log file space for message queues in themessaging component. The rules engine in turn can apply management rulesto the tokens in the working memory in order to direct managementactions in the messaging component.

As a result of the tight coupling of the rules engine to the messagingcomponent using the working memory in the shared memory, the rulesengine can provide an alternative view of messaging data allowing formore flexibility in the management of the message oriented middleware.Further, as the rules engine through a sharing of the working memorywith the messaging component becomes part of the message orientedmiddleware, the rules engine has open access to the data known to themessaging system. Of import, based upon the tight coupling of the rulesengine with the messaging component, the rules engine is not limited bycommunications latencies in detecting conditions in the messagingcomponent.

In further illustration, FIG. 1 is a pictorial illustration of a processfor managing a messaging component in message oriented middleware. Asshown in FIG. 1, message oriented middleware 100 can include both amessaging component 150 and a rules engine 130 coupled to the messagingcomponent 150 by way of shared memory 140. Messaging component 150 canmanage different objects 160 subsisting in the message orientedmiddleware 160, for example message queues, messages in message queues,topics or subscriptions or log file space for message queues and thelike. Messaging component 150 further can create in the shared memory140, tokens 120 each token corresponding to one of the objects 160. Therules engine 130, in turn, can monitor the shared memory 140 and canapply rules 110 to the tokens 120 in the shared memory 140. In this way,the rules 110 of the rules engine 130 can be applied without delay tochanges in the objects 160 reflected by corresponding changes in thetokens 120.

The process described in connection with FIG. 1 can be implementedwithin a message data processing system. In yet further illustration,FIG. 2 schematically shows a message data processing system configuredwith an integrated rules engine for managing a messaging component inmessage oriented middleware. The system can include a host server 200configured for communicative coupling to different client computers 205over computer communications network 215. The host server 200 caninclude at least one processor 220 and memory 230 supporting theexecution of operating system 240. The operating system 240 in turn canhost the operation of message oriented middleware 250 that includes atleast one messaging component 260 managing message exchanges in one ormore message queues (not shown).

As shown in FIG. 2, rules engine 270 can be coupled to the messagingcomponent 260 and can apply one or more messaging component managementrules (not shown) to tokens in working memory 270 in order to directmanagement operations in the messaging component 260. Of note, a rulesengine integration module 300 can be coupled to the messaging component260. The module 300 can include program code enabled to monitor thecreation, deletion and modification of objects in the messagingcomponent 260 such as message queues or messages within message queues,or topics or subscriptions or log file space for message queues, and tomaintain corresponding tokens in the working memory 270. In this way,the rules engine 270 can apply the rules to the tokens when changesoccur in the tokens which contemporaneously relate to objects in themessaging component 260.

In yet further illustration of the operation of the rules engineintegration module 300, FIG. 3 is a flow chart illustrating a processfor managing a messaging component in message oriented middleware. Asshown in FIG. 3, the messaging component and rules engine can actasynchronously to contemporaneously communicate object changes in themessaging component through the use tokens of shared memory so that therules engine can respond to changes in the tokens with the applicationof one or more management rules to the tokens to direct managementoperations in the messaging component. Beginning in block 310, a changecan be detected in an object in the messaging component. In block 320,it can be determined if the change is the addition of a new component.If so, in block 330 a corresponding token can be created in sharedmemory. Otherwise, the process can continue through block 340.

In block 340, a token corresponding to the changed object can beselected in the shared memory. Thereafter, in decision block 350, it canbe determined whether or not the change to the object in the messagingcomponent is the removal of the object. If so, in block 360 the selectedtoken can be removed from shared memory. Otherwise, in decision block370 it can be determined whether or not the change to the object is amodification of the characteristics of the object. If so, in block 380 acorresponding indication of the modification of the characteristics canbe applied to the selected token in shared memory.

Concurrently with the operation of the messaging component, in block 390the rules engine can monitor changes to tokens in the shared memory. Indecision block 400, it can be determined whether or not a token inshared memory has changed. If so, in block 410, one or more rules can beapplied to the token to determine a course of action to be directed inthe messaging component by the rules engine.

As will be appreciated by one skilled in the art, aspects of the presentinvention may be embodied as a system, method or computer programproduct. Accordingly, aspects of the present invention may take the formof an entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.) or anembodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module” or “system.”Furthermore, aspects of the present invention may take the form of acomputer program product embodied in one or more computer readablemedium(s) having computer readable program code embodied thereon.

Any combination of one or more computer readable medium(s) may beutilized. The computer readable medium may be a computer readable signalmedium or a computer readable storage medium. A computer readablestorage medium may be, for example, but not limited to, an electronic,magnetic, optical, electromagnetic, infrared, or semiconductor system,apparatus, or device, or any suitable combination of the foregoing. Morespecific examples (a non-exhaustive list) of the computer readablestorage medium would include the following: an electrical connectionhaving one or more wires, a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), an optical fiber,a portable compact disc read-only memory (CD-ROM), an optical storagedevice, a magnetic storage device, or any suitable combination of theforegoing. In the context of this document, a computer readable storagemedium may be any tangible medium that can contain, or store a programfor use by or in connection with an instruction execution system,apparatus, or device.

A computer readable signal medium may include a propagated data signalwith computer readable program code embodied therein, for example, inbaseband or as part of a carrier wave. Such a propagated signal may takeany of a variety of forms, including, but not limited to,electro-magnetic, optical, or any suitable combination thereof. Acomputer readable signal medium may be any computer readable medium thatis not a computer readable storage medium and that can communicate,propagate, or transport a program for use by or in connection with aninstruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmittedusing any appropriate medium, including but not limited to wireless,wireline, optical fiber cable, radiofrequency, and the like, or anysuitable combination of the foregoing. Computer program code forcarrying out operations for aspects of the present invention may bewritten in any combination of one or more programming languages,including an object oriented programming language and conventionalprocedural programming languages. The program code may execute entirelyon the user's computer, partly on the user's computer, as a stand-alonesoftware package, partly on the user's computer and partly on a remotecomputer or entirely on the remote computer or server. In the latterscenario, the remote computer may be connected to the user's computerthrough any type of network, including a local area network (LAN) or awide area network (WAN), or the connection may be made to an externalcomputer (for example, through the Internet using an Internet ServiceProvider).

Aspects of the present invention have been described above withreference to flowchart illustrations and/or block diagrams of methods,apparatus (systems) and computer program products according toembodiments of the invention. In this regard, the flowchart and blockdiagrams in the Figures illustrate the architecture, functionality, andoperation of possible implementations of systems, methods and computerprogram products according to various embodiments of the presentinvention. For instance, each block in the flowchart or block diagramsmay represent a module, segment, or portion of code, which comprises oneor more executable instructions for implementing the specified logicalfunction(s). It should also be noted that, in some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts, or combinations of special purpose hardware andcomputer instructions.

It also will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. These computer program instructions maybe provided to a processor of a general purpose computer, specialpurpose computer, or other programmable data processing apparatus toproduce a machine, such that the instructions, which execute via theprocessor of the computer or other programmable data processingapparatus, create means for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computerreadable medium that can direct a computer, other programmable dataprocessing apparatus, or other devices to function in a particularmanner, such that the instructions stored in the computer readablemedium produce an article of manufacture including instructions whichimplement the function/act specified in the flowchart and/or blockdiagram block or blocks. The computer program instructions may also beloaded onto a computer, other programmable data processing apparatus, orother devices to cause a series of operational steps to be performed onthe computer, other programmable apparatus or other devices to produce acomputer implemented process such that the instructions which execute onthe computer or other programmable apparatus provide processes forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

Finally, the terminology used herein is for the purpose of describingparticular embodiments only and is not intended to be limiting of theinvention. As used herein, the singular forms “a”, “an” and “the” areintended to include the plural forms as well, unless the context clearlyindicates otherwise. It will be further understood that the terms“comprises” and/or “comprising,” when used in this specification,specify the presence of stated features, integers, steps, operations,elements, and/or components, but do not preclude the presence oraddition of one or more other features, integers, steps, operations,elements, components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below are intended toinclude any structure, material, or act for performing the function incombination with other claimed elements as specifically claimed. Thedescription of the present invention has been presented for purposes ofillustration and description, but is not intended to be exhaustive orlimited to the invention in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the artwithout departing from the scope and spirit of the invention. Theembodiment was chosen and described in order to best explain theprinciples of the invention and the practical application, and to enableothers of ordinary skill in the art to understand the invention forvarious embodiments with various modifications as are suited to theparticular use contemplated.

Having thus described the invention of the present application in detailand by reference to embodiments thereof, it will be apparent thatmodifications and variations are possible without departing from thescope of the invention defined in the appended claims as follows:
 1. Amethod for managing a messaging component in message orientedmiddleware, the method comprising: establishing working memory in sharedmemory of the message oriented middleware executing by a processor of acomputer for use by the messaging component; detecting a change in themessaging component; determining if the change corresponds to anaddition of an object to the message component and, on condition thechange corresponds to an addition of a new object to the messagecomponent, creating a token in the working memory, but on condition thechange corresponds to a deletion of an existing object from the messagecomponent, deleting a token from the working memory, and on conditionthe change corresponds to a change to an existing object of the messagecomponent that is not a deletion of the existing object, applying achange to an existing token in the working memory; observing the workingmemory to detect changes in one or more tokens in the working memory;and, in response to detecting a change to one or more of the tokens inthe working memory, applying management rules, by a rules engine and amessaging engine, to the tokens in the working memory in order to directmanagement actions in the messaging component; wherein the rules engineand the messaging engine are sufficiently closely coupled so that thereis no significant exchange of synchronization data between the rulesengine and the messaging engine, by using the shared memory so that themessaging engine has access to the data known to a queue manager and isnot limited by slow network connections.
 2. The method of claim 1wherein: the rules engine and messaging engine further ensure thattokens in the memory correspond to objects in the messaging engine. 3.The method of claim 2 wherein: the rules engine and messaging enginefurther put a message on a queue, insert a token corresponding themessage in memory, and link the token to the corresponding message.
 4. Amessage processing data processing system comprising: a host computerwith at least one processor and memory; shared memory established withinthe memory of the host computer; a messaging component managing aplurality of message queues in the memory; a rules engine applying aplurality of rules to tokens in the shared memory and directingmanagement operations in the messaging component responsive to theapplied rules by the rules engine; and, a rules engine integrationmodule coupled to the messaging component, the module comprising programcode enabled to perform: establishing working memory in the sharedmemory; detecting a change in the messaging component; determining ifthe change corresponds to an addition of an object to the messagecomponent and, on condition the change corresponds to an addition of anew object to the message component, creating a token in the workingmemory, but on condition the change corresponds to a deletion of anexisting object from the message component, deleting a token from theworking memory, and on condition the change corresponds to a change toan existing object of the message component that is not a deletion ofthe existing object, applying a change to an existing token in theworking memory; observing the working memory to detect changes in one ormore tokens in the working memory; and, in response to detecting achange to one or more of the tokens in the working memory, applyingmanagement rules, by a rules engine and a messaging engine, to thetokens in the working memory in order to direct management actions inthe messaging component; wherein the rules engine and the messagingengine are sufficiently closely coupled so that there is no significantexchange of synchronization data between the rules engine and themessaging engine, by using the shared memory so that the messagingengine has access to the data known to a queue manager and is notlimited by slow network connections.
 5. The system of claim 4 wherein:the rules engine and messaging engine further ensure that tokens in thememory correspond to objects in the messaging engine.
 6. The system ofclaim 5 wherein: the rules engine and messaging engine further put amessage on a queue, insert a token corresponding the message in memory,and link the token to the corresponding message.
 7. A computer programproduct for managing a messaging component in message orientedmiddleware, the computer program product comprising a non-transitorycomputer readable storage medium having computer readable program codeembodied therewith, the computer readable program code performing:establishing working memory in shared memory of the message orientedmiddleware executing by a processor of a computer for use by themessaging component; detecting a change in the messaging component;determining if the change corresponds to an addition of an object to themessage component and, on condition the change corresponds to anaddition of a new object to the message component, creating a token inthe working memory, but on condition the change corresponds to adeletion of an existing object from the message component, deleting atoken from the working memory, and on condition the change correspondsto a change to an existing object of the message component that is not adeletion of the existing object, applying a change to an existing tokenin the working memory; observing the working memory to detect changes inone or more tokens in the working memory; and, in response to detectinga change to one or more of the tokens in the working memory, applying bya rules engine and a messaging engine management rules to the tokens inthe working memory in order to direct management actions in themessaging component; wherein the rules engine and the messaging engineare sufficiently closely coupled so that there is no significantexchange of synchronization data between the rules engine and themessaging engine, by using the shared memory so that the messagingengine has access to the data known to a queue manager and is notlimited by slow network connections.
 8. The computer program product ofclaim 7 wherein: the rules engine and messaging engine further ensurethat tokens in the memory correspond to objects in the messaging engine.9. The computer program product of claim 8 wherein: the rules engine andmessaging engine further put a message on a queue, insert a tokencorresponding the message in memory, and link the token to thecorresponding message.